Synchronizing Date and Time through SIP
You can configure the device to synchronize its internal clock (date and time) with a remote SIP endpoint (according to RFC 3261). When enabled, the device obtains the date and time from the Date header in the incoming 200 OK message received in response to a REGISTER request sent by the device. This can be any REGISTER request sent for normal SIP traffic handling (i.e., it's not a specific REGISTER message that is sent to a specific SIP server or endpoint). An example of a SIP Date header with date and time is shown below:
Date: Sat, 12 Mar 2020 23:29:00 GMT
|
➢
|
To configure clock synchronization through SIP: |
|
1.
|
Open the Time & Date page (Setup menu > Administration tab > Time & Date), and then scroll down to the Date Header Time Sync group: |
|
2.
|
In the 'Synchronize Time from SIP Date Header' [DateHeaderTimeSync] field, select Enable to enable the feature. |
|
3.
|
In the 'Time Synchronization Interval' [DateHeaderTimeSyncInterval] field, enter the minimum time (in seconds) between synchronization updates. For example, if configured to 8640 (24 hours) and the device receives within this 24-hour interval a SIP response to a REGISTER with the Date header, it ignores the date. Only if it receives such a header after this interval does it update its clock according to the header, and then does the next update 24 hours later. |
|
4.
|
Click Apply. When the device receives a SIP response with the Date header, it updates its clock and the date and time is displayed in the 'UTC Time' read-only field under the Time group (see Viewing Date and Time). |
|
●
|
The device only uses the date and time in the SIP Date header if its value is year 2016 or later. |
|
●
|
If you have enabled clock synchronization using an NTP server (see Synchronizing Date and Time through SNTP) and using the SIP Date header, synchronization using the NTP server takes precedence (i.e., device ignores received Date headers). When both are enabled, the device sends the SNMP alarm acClockConfigurationAlarm. |
|
●
|
Once a week, the device stores the clock's date and time in its flash memory. If the device is restarted, its clock is set to this stored date and time, and updated once it receives a Date header in a SIP response to a sent REGISTER message. |
|
●
|
Synchronization by NTP takes highest preference, and then by SIP Date header. For example, if you enable NTP, the device ignores the SIP Date header settings. If you do enable multiple synchronization methods, the device sends the SNMP alarm acClockConfigurationAlarm to notify you of this configuration scenario. |